Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
IBM System Display and Search Facility (SDSF) Started task will be properly defined to the STARTED resource class for RACF.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-224510 | ZISFR032 | SV-224510r840223_rule | Medium |
| Description |
|---|
| Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data. |
| STIG | Date |
|---|---|
| z/OS IBM System Display and Search Facility (SDSF) for RACF Security Technical Implementation Guide | 2022-06-27 |
Details
| Check Text ( C-26193r840221_chk ) |
|---|
| Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZISF0032) If the IBM SDSF started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding. |
| Fix Text (F-26181r840222_fix) |
|---|
| The ISSO working with the systems programmer will ensure the IBM SDSF Started Task(s) is properly identified and/or defined to the System ACP. A unique userid must be assigned for the IBM SDSF started task(s) thru a corresponding STARTED class entry. The following commands are provided as a sample for defining Started Task(s): rdef started SDSF.** uacc(none) owner(admin) audit(all(read)) – stdata(user(SDSF) group(stc)) setr racl(started) ref |